Add Veo plugin - #553

Summary

Add a separately searchable Veo third-party Cursor plugin. It reuses the existing Ace Data Cloud hosted veo MCP, a focused Agent skill, and the exact service logo from the Ace Data Cloud Veo integration. The English and Chinese guides cover installation, service API key, permissions, one first-run prompt, task retrieval where applicable, result inspection, Credits, and troubleshooting.

Standalone source is reviewable at AceDataCloud/VeoCursor#1 and its exact commit AceDataCloud/VeoCursor@0d8e51b. This is a tool plugin, not a Cursor chat-model provider.

Validation

• Official node scripts/validate-plugins.mjs: passed with this marketplace entry.

• git diff --check: passed. Logo SHA-256: 26bf44b131bf91b6e7b4ce1df82925346b7e850583d8f5fa8f449d4350fd5af8.

• Authenticated hosted MCP tools/list exposed veo_text_to_video and veo_get_task; its live schema includes the first-run parameters. This is a read-only tool/schema check, not a claim of a new paid generation or a Cursor UI install.

• On 2026-10-12, an authenticated read-only task query against the hosted MCP returned a completed historical result and an HTTPS media URL. No new paid generation was submitted. This is direct MCP validation, not a Cursor Agent UI call or Marketplace installation.

Publication state

This PR is a formal submission. Review, merge, Marketplace listing and search, user installation, and a Cursor Agent call remain separate gates. Cursor 3.24.12 is signed in; this plugin's own UI installation and Agent call have not yet been verified. No credential is committed.

README attribution: the shared English/Chinese CTA links are tagged with opensource / referral / evergreen, with service/Cursor/language content values. Matching source documentation is proposed at AceDataCloud/VeoCursor#2. This is a documentation-only update; source merge, official indexing, public search/install and measured activation remain separate gates.

2026-10-14 base refresh

Rebased onto current official main ce649c03ac3b75b6ae80cbd15b7e2c536caedb5a. The catalog and root README retain all 102 upstream entries and their existing content, plus this plugin's original entry. The plugin directory tree remains byte-for-byte identical (09a103faa9662317e4dd71689577aa187c872ddd), including its HTTP MCP config, API token declaration, skill, and bilingual UTM links.

Validation for the published tree b1facf38b1f3ced309af54f750b2834b817d3b02 at head ca08ea8a3f5f4a9612387769c67c6fa740701dc7: node scripts/validate-plugins.mjs and git diff --check pass, and merge-tree with the pinned base is clean. GitHub updateRefs was used with an atomic beforeOid lease after the ordinary Git HTTPS transport timed out. This maintains the existing submission; Marketplace approval, installation, and host acceptance remain separate stages.

2026-10-15 base refresh

Rebased onto current official main 850d7f2e9f5e55dff7eb00a0a479337fe79eb22f. The catalog and root README retain all 104 upstream entries and their existing content, plus this plugin's original entry. The plugin directory tree remains byte-for-byte identical (09a103faa9662317e4dd71689577aa187c872ddd), including its HTTP MCP config, API token declaration, skill, and bilingual UTM links.

Validation for the published tree 32d921beee723e999036489be2ab11f10bcc21a3 at head d6bf318f3110679c80fa3a262c99265a7680fc9b: node scripts/validate-plugins.mjs and git diff --check pass, and merge-tree with the pinned base is clean. GitHub updateRefs was used with an atomic beforeOid lease after the ordinary Git HTTPS transport timed out. This maintains the existing submission; Marketplace approval, installation, and host acceptance remain separate stages.

2026-10-18 native-distribution update

Updated onto current official main 101b274dd991f694e1f7024be2157e5f3adf07de. All 109 existing catalog entries and the full upstream README are preserved, including the revised Tailscale text. The plugin directory remains unchanged (09a103faa9662317e4dd71689577aa187c872ddd). This update only resolves the catalog/root README conflict against the latest official base.

Validation at 3c5f82171528332b94b581583be19639816675e5: current node scripts/validate-plugins.mjs, node scripts/generate-pstack-harness-trees.mjs --check, git diff --check and merge-tree pass. Published Git commit/tree SHAs equal the locally validated objects. Every original OPEN branch update uses atomic beforeOid comparison. No duplicate submission, PR merge, deployment, paid generation or publisher agreement acceptance. Official review, live service-name search, installation and actual Cursor use remain separate gates.

2026-10-19 merged source and versioned release

Source AceDataCloud/VeoCursor#2 is now merged at f2631c769ba66fecbf4f08de1b34276be38aa6b4 and the Git-distributed plugin source release v1.0.0 is public: https://github.com/AceDataCloud/VeoCursor/releases/tag/v1.0.0. Tag and manifest version match the merged commit. ZIP/source receipt/SHA256SUMS were published, downloaded and verified byte-for-byte and per-file. The final source PR only added the standard four-field acquisition queries to existing bilingual platform links; no runtime/Auth/Skills/model/price/route/fallback changes.

This preserves the existing official submission and its head 3c5f82171528332b94b581583be19639816675e5. Source release is not official Marketplace acceptance/indexing or actual native Cursor installation/Configure E2E; those remain separate. No duplicate publisher identity, terms acceptance or paid generation was performed. The official Actions execution gate is still recorded separately. Public source/main/tag now removes the pending own-PR gate and supplies immutable review artifacts.